Wireless user equipment (UE) registration with networking data responsive to external control

ABSTRACT

A wireless communication network comprises a Network Exposure Function (NEF) and an Access and Mobility Management Function (AMF) to register a User Equipment (UE). The NEF receives a NEF Application Programming Interface (API) call that has a UE instruction. The NEF translates the NEF API call having the UE instruction into an AMF API call that has the UE instruction. The NEF transfers the AMF API call to the AMF. The AMF translates the UE instruction into a registration message that has a registration cause. The AMF transfers the registration message that has the registration cause to the UE. The UE receives the registration message, and in response, identifies networking data based on the registration cause and performs a registration based on the networking data.

TECHNICAL BACKGROUND

Wireless communication networks provide wireless data services towireless user devices. Exemplary wireless data services includemachine-control, internet-access, media-streaming, andsocial-networking. Exemplary wireless user devices comprise phones,computers, vehicles, robots, and sensors. The wireless user devicesexecute user applications to support and use the wireless data services.For example, a robot may execute a machine-control application thatcommunicates with a robot controller over a wireless communicationnetwork.

The wireless communication networks have wireless access nodes whichexchange wireless signals with the wireless user devices over radiofrequency bands. The wireless signals use wireless network protocolslike Fifth Generation New Radio (5GNR), Long Term Evolution (LTE),Institute of Electrical and Electronic Engineers (IEEE) 802.11 (WIFI),and Low-Power Wide Area Network (LP-WAN). The wireless access nodesexchange network signaling and user data with network elements that areoften clustered together into wireless network cores. The networkelements comprise Access and Mobility Management Functions (AMFs),Session Management Functions (SMFs), Interworking functions (IWFs), UserPlane Functions (UPFs), Network Exposure Functions (NEFs), ApplicationFunctions (AFs), and the like. The wireless communication networks maycomprise Public Land Mobile Networks (PLMNs) that use different wirelessaccess technologies and different radio frequency bands. The wirelessnetwork elements are grouped into different Dynamic Network Names (DNNs)and wireless network slices.

A wireless user device initially registers with a network controllerlike an Access and Mobility Management Function (AMF) over a wirelessaccess node. The wireless user device and the network controllerexchange data to authenticate the identity of the wireless user deviceand to identify qualified services for the wireless user device. Thenetwork controller selects parameters like frequency band, access node,DNN, slice, and the like for the qualified services. The wireless userdevice may also select or request parameters like frequency band, accessnode, PLMN, slice, and the like. In some cases, the network controllerdirects the wireless user device to deregister and reregister on a newfrequency band. The network controller may direct the wireless userdevice to handover to a new access node that will require a newregistration. The network controller may direct the wireless user deviceto re-authenticate which requires a new registration. Unfortunately, thenetwork controller does not effectively direct registrations based onexternal control from a user application server. Moreover, the networkcontroller does not efficiently direct registrations to inject newnetworking data like a new PLMN, DNN, or slice in response to theexternal application server.

TECHNICAL OVERVIEW

A wireless communication network comprises a Network Exposure Function(NEF) and an Access and Mobility Management Function (AMF) to register aUser Equipment (UE). The NEF receives a NEF Application ProgrammingInterface (API) call that has a UE instruction. The NEF translates theNEF API call having the UE instruction into an AMF API call that has theUE instruction. The NEF transfers the AMF API call to the AMF. The AMFtranslates the UE instruction into a registration message that has aregistration cause. The AMF transfers the registration message that hasthe registration cause to the UE. The UE receives the registrationmessage, and in response, identifies networking data based on theregistration cause and performs a registration based on the networkingdata.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network that has a NetworkExposure Function (NEF) and an Access and Mobility Management Function(AMF) to register a User Equipment (UE).

FIG. 2 illustrates an exemplary operation of the wireless communicationnetwork that has the NEF and the AMF to register the UE.

FIG. 3 illustrates an exemplary operation of the wireless communicationnetwork that has the NEF and the AMF to register the UE.

FIG. 4 illustrates a Fifth Generation (5G) wireless communicationnetwork that has a NEF and AMF to register a UE.

FIG. 5 illustrates the UE in the 5G wireless communication network.

FIG. 6 illustrates the WIFI access node in the 5G wireless communicationnetwork.

FIG. 7 illustrates the LTE access node in the 5G wireless communicationnetwork.

FIG. 8 illustrates a wireless network core in the 5G wirelesscommunication network.

FIG. 9 further illustrates the wireless network core in the 5G wirelesscommunication network.

FIG. 10 illustrates an exemplary operation of the 5G wirelesscommunication network to register the UE.

DETAILED DESCRIPTION

FIG. 1 illustrates wireless communication network 100 that has NetworkExposure Function (NEF) 123 and Access and Mobility Management Function(AMF) 122 to register User Equipment (UE) 101. UE 101 comprises acomputer, phone, vehicle, sensor, robot, or some other data appliancewith communication circuitry. Wireless communication network 100delivers services to UE 101 like internet-access, machine-control,media-streaming, or some other data communications product. Wirelesscommunication network 100 comprises UE 101, Radio Access Network (RAN)121, AMF 122, NEF 123, and network functions 124.

Various examples of network operation and configuration are describedherein. In some examples, NEF 123 receives a NEF Application ProgrammingInterface (API) call that has a UE instruction. The NEF API call maycome from an Application Function (AF) that is controlled by ApplicationServer (AS) 102. NEF 123 translates the NEF API call that has the UEinstruction into an AMF API call that has the UE instruction. NEF 123transfers the AMF API call that has the UE instruction to AMF 122. AMF122 translates the UE instruction into a registration message that has aregistration cause. AMF 122 transfers the registration message that hasthe registration cause to UE 101 over RAN 121 or another access network.In response to the registration message, UE 101 identifies networkingdata based on the registration cause and performs a new registrationbased on the networking data over RAN 121 or the other access network.

In some examples, the UE instruction requests a UE ID authentication forUE 101, and the registration cause indicates an immediate AMFre-registration to re-authenticate the UE ID in UE 101. In response tothe registration cause, UE 101 and AMF 122 perform a new AMFregistration to authenticate the UE ID in UE 101. In some examples, theUE instruction requests a new AMF, wireless network slice, and/orDynamic Network Name (DNN) for UE 101. The registration cause indicatesthe new AMF, slice, and/or DNN to use in an AMF re-registration. Inresponse to the registration cause, UE 101 and AMF 122 or a new AMFperform a new registration to use the new AMF, slice, and/or DNN for UE101. In some examples, the UE instruction requests a new frequency band,access node, Public Land Mobile Network (PLMN), and/or reboot procedurefor UE 101. The registration cause indicates the new frequency band,access node, PLMN, and/or reboot procedure to use in a RANre-registration. In response to the registration cause, UE 101 and RAN121 or the other access network perform a new access networkregistration to use the new frequency band, access node, PLMN, and/orreboot procedure for UE 101.

Advantageously, AMF 122 and NEF 123 effectively direct UE registrationsbased on external control from AS 102. Moreover, AMF 122 and NEF 123efficiently direct the UE registrations to inject new networking datalike a new PLMN, DNN, or slice in response to the external control fromAS 102.

UE 101 communicates with RAN 121 over technologies like Fifth GenerationNew Radio (5GNR), Long Term Evolution (LTE), Low-Power Wide Area Network(LP-WAN), Institute of Electrical and Electronic Engineers (IEEE) 802.11(WIFI), Bluetooth, Narrowband Internet-of-Things (NB-IoT), and/or someother wireless networking protocol. The wireless communicationtechnologies use electromagnetic frequencies in the low-band, mid-band,high-band, or some other portion of the electromagnetic spectrum. Thecommunication links that interconnect wireless communication network 100use metallic links, glass fibers, radio channels, or some othercommunication media. The communication links use IEEE 802.3 (ENET),Internet Protocol (IP), Time Division Multiplex (TDM), Data Over CableSystem Interface Specification (DOCSIS), General Packet Radio ServiceTransfer Protocol (GTP), 3GPP, 5GNR, LTE, WIFI, virtual switching,inter-processor communication, bus interfaces, and/or some other datacommunication protocols. UE 101 communicates with AMF 122 and networkfunctions 124 over RAN 121. UE 101 may also communicate with AMF 122 andnetwork functions 124 over wireline access networks like InternetService Providers (ISPs).

UE 101 and RAN 121 comprise antennas, amplifiers, filters, modulation,analog/digital interfaces, microprocessors, software, memories,transceivers, bus circuitry, and the like. AMF 122, NEF 123, and networkfunctions 124 comprise microprocessors, software, memories,transceivers, bus circuitry, and the like. The microprocessors compriseDigital Signal Processors (DSP), Central Processing Units (CPU),Graphical Processing Units (GPU), Application-Specific IntegratedCircuits (ASIC), and/or the like. The memories comprise Random AccessMemory (RAM), flash circuitry, disk drives, and/or the like. Thememories store software like operating systems, user applications, radioapplications, and network functions. The microprocessors retrieve thesoftware from the memories and execute the software to drive theoperation of wireless communication network 100 as described herein.

FIG. 2 illustrates an exemplary operation of wireless communicationnetwork 100 that has NEF 123 and AMF 122 to register UE 101. Thisoperation is exemplary and may vary in other examples. NEF 123 receivesa NEF Application Programming Interface (API) call that has a UEinstruction (201). NEF 123 detects the UE instruction (202), and inresponse, NEF 123 translates the NEF API call that has the UEinstruction into an AMF API call that has the UE instruction (203). NEF123 transfers the AMF API call that has the UE instruction to AMF 122(203). AMF 122 receives the AMF API call that has the UE instruction(204). AMF 122 detects the UE instruction (205), and in response, AMF122 translates the UE instruction into a registration message that has aregistration cause (206). AMF 122 transfers the registration messagethat has the registration cause to UE 101 (206). UE 101 receives theregistration message that has the registration cause, and in response,UE 101 identifies networking data based on the registration cause (207).UE 101 performs a new registration based on the networking data over RAN121 or another access network (207).

FIG. 3 illustrates an exemplary operation of wireless communicationnetwork 100 that has NEF 123 and AMF 122 to register UE 101. Thisoperation is exemplary and may vary in other examples. NEF 123 receivesa NEF API call that has an instruction for UE 101. UE 101 wirelesslyattaches to RAN 121 and transfers an AMF registration request to AMF 122over RAN 121. In response to a previous NEF event subscription for UE101, AMF 122 transfers a registration notice for UE 101 to NEF 123. Inresponse to the NEF API call and the registration notice for UE 101, NEF123 translates the NEF API call that has the UE instruction into an AMFAPI call that has the UE instruction. NEF 123 transfers the AMF API callthat has the UE instruction to AMF 122. AMF 122 translates the UEinstruction into a registration rejection that has a registration cause.The registration cause comprises coded instructions to re-register withnew networking data at a future time or in response to a futurecondition. AMF 122 transfers an AMF registration rejection that has theregistration cause to UE 101 over RAN 121. In response to theregistration message, UE 101 identifies networking data and the futuretime or condition. UE 101 transfers another AMF registration request toAMF 122 over RAN 121 using the network data in response to theoccurrence of the future time or condition. AMF 122 performs the AMFregistration based on the networking data. The networking data coulddrive AMF 122 to use a new slice, DNN, quality, or the like for UE 101.UE 101 and RAN 121 exchange user data under the direction of AMF 122.RAN 121 exchanges the user data with network functions 124 under thedirection of AMF 122.

FIG. 4 illustrates Fifth Generation (5G) wireless communication network400 that has NEF 424 and AMF 423 to register UE 401. 5G wirelesscommunication network 400 comprises an example of wireless communicationnetwork 100, although network 100 may vary from this example. 5Gwireless communication network 400 comprises UE 401, WIFI AN 420, 5GNRAN 421, Non-Third Generation Partnership Project (N3GPP) IWF 422, Accessand Mobility Management Function (AMF) 423, Network Exposure Function(NEF) 424, Application Function (AF) 425, Session Management Function(SMF) 426, User Plane Function (UPF) 427, AMF 433, SMF 436, and UPF 437.

AS 402 transfers an instruction for UE 101 to AF 425. The userinstruction may indicate when the user instruction should beimplemented—immediately, a future time, or in response to a futureevent. For example, UE 401 may be a carbon dioxide sensor, and theinstruction could be to re-register when the carbon dioxide levelexceeds a reporting threshold. The user instruction may indicate aregistration technique—after UE reboot, RAN registration, new accessnetwork registration, AMF registration, or new AMF registration, and thelike. For example, UE 401 may reboot an operating system and thenre-register with new AMF 433. The user instruction may indicate newregistration data for PLMN, frequency band, access node, AMF, slice,DNN, and the like. For example, UE 401 may deregister and go dormantuntil late-night, and then register with new PLMN for a contentdownload. AF 425 translates the user instruction from AS 402 into anorthbound API call. AF 425 transfers northbound API call to NEF 424.

NEF 424 translates the NEF API call that has the UE instruction into anAMF API call that has the UE instruction. The translation may entail theabstraction of network data. In some cases, NEF 424 awaits a time orother condition like UE registration to generate the AMF API call.Eventually, NEF 424 transfers the AMF API call that has the UEinstruction to AMF 423. AMF 423 translates the UE instruction into aregistration message that has a registration cause. For example, AMF 423may map registration instructions for time, condition, technique, andnetworking data into alpha-numeric codes that are added to an existingcause and that are understood by UE 401. AMF 423 transfers theregistration message with the registration cause to UE 401 over ANs420-421.

In response to the registration message, UE 401 identifies networkingdata based on the registration cause. For example, UE 401 may host adata structure that translates alpha-numeric codes into registrationinstructions. UE 401 identifies how and when to perform the newregistration based on the registration cause. UE 401 performs thespecified type of registration based at the appropriate time using theselect networking data. For example, UE 401 may register with 5GNR AN421 to use a new PLMN and/or new AMF 433. UE 401 may register with AMF423 to use a new slice and/or DNN. UE 401 may reboot hardware and/orsoftware before registering with ANs 421 or 422 with AMFs 423 or 433. AS402 drives various operations over 5G wireless communication network400. AS 402 can specify a new registration to change frequency bands,access nodes, PLMNs, AMFs, DNNs, slices, and the like. For example, AS402 may drive 5G network 400 to de-register UE 401 from AMF 423 and itscurrent DNN and to re-register UE 401 with AMF 433 and a new DNN.

FIG. 5 illustrates UE 401 in 5G wireless communication network 400. UE401 comprises an example of UE 101, although UE 101 may differ. UE 401comprises WIFI radio 501, 5GNR radio 502, processing circuitry 503, anduser components 504. Radios 501-502 comprise antennas, amplifiers,filters, modulation, analog-to-digital interfaces, DSP, memory, andtransceivers that are coupled over bus circuitry. Processing circuitry503 comprises memory, CPU, user interfaces and components, andtransceivers that are coupled over bus circuitry. The memory inprocessing circuitry 503 stores an operating system, user applications(USER), and network applications for IP, 3GPP, WIFI, and 5GNR. Thenetwork applications include physical layer, media access control, linkcontrol, convergence and adaption, radio resource control, and the like.The antennas in WIFI radio 501 are wirelessly coupled to WIFI AN 420over a WIFI link that supports NWu and N1. The antennas in 5GNR radio502 are wirelessly coupled to 5GNR AN 421 over a 5GNR link that supportsRRC and N1. Transceivers (XCVRs) in radios 501-502 are coupled totransceivers in processing circuitry 503. Transceivers in processingcircuitry 503 are coupled to user components 504 like displays,controllers, and memory. The CPU in processing circuitry 503 executesthe operating system, user applications, and network applications toexchange network signaling and user data with respective ANs 420-421over respective radios 501-502.

FIG. 6 illustrates WIFI AN 420 in 5G wireless communication network 400.WIFI AN 420 comprises an example of RAN 121, although RAN 121 maydiffer. WIFI AN 420 comprises WIFI radio 601 and node circuitry 602.WIFI radio 601 comprises antennas, amplifiers, filters, modulation,analog-to-digital interfaces, DSP, memory, and transceivers that arecoupled over bus circuitry. Node circuitry 602 comprises memory, CPU,and transceivers that are coupled over bus circuitry. The memory in nodecircuitry 602 stores operating systems and network applications for IP,WIFI, and 3GPP like physical layer, media access control, link control,and the like. The antennas in WIFI radio 601 are wirelessly coupled toUE 401 over wireless links that support NWu and N1. Transceivers in WIFIradio 601 are coupled to transceivers in node circuitry 602, andtransceivers in node circuitry 602 are coupled to transceivers in IWF422 over links that support NWu and N1. The CPU in node circuitry 602executes the operating system and network applications to exchange dataand signaling with UE 401 and to exchange data and signaling with IWF422.

FIG. 7 illustrates 5GNR AN 421 in 5G wireless communication network 400.5GNR AN 421 comprises an example of RAN 121, although RAN 121 maydiffer. 5GNR AN 421 comprises 5GNR Radio Unit (RU) 701, 3GPP DistributedUnit (DU) 702, and 3GPP Centralized Unit (CU) 703. 5GNR RU 701 comprisesantennas, amplifiers, filters, modulation, analog-to-digital interfaces,DSP, memory, and transceivers that are coupled over bus circuitry. DU702 comprises memory, CPU, and transceivers that are coupled over buscircuitry. The memory in DU 702 stores operating systems and 5GNRnetwork applications that include Physical Layer (PHY), Media AccessControl (MAC), Radio Link Control (RLC), and the like. CU 703 comprisesmemory, CPU, and transceivers that are coupled over bus circuitry. Thememory in CU 703 stores an operating system and network applications forIP and 5GNR that include Packet Data Convergence Protocol (PDCP),Service Data Adaption Protocol (SDAP), Radio Resource Control (RRC), andthe like. The antennas in RU 701 are wirelessly coupled to UE 401 over5GNR links that use various frequency bands and that support RRC and N1.Transceivers in RU 701 are coupled to transceivers in DU 702 overfronthaul links like enhanced Common Public Radio Interface (eCPRI).Transceivers in DU 702 coupled to transceivers in CU 703 over mid-haullinks. Transceivers in CU 703 are coupled to AMF 423 and UPF 427 overbackhaul links. The CPU in DU 703 executes an operating system andnetwork applications to exchange 5GNR data units with RU 701 and toexchange 5GNR data units with CU 703. The CPU in CU 703 executes anoperating system and network applications to exchange the 5GNR dataunits with DU 702, exchange N2/N1 signaling with AMF 423, and exchangeN3 data with UPF 427.

FIG. 8 illustrates wireless network core 800 in 5G wirelesscommunication network 400. Network core 800 comprises an example of AMF122, NEF 123, and network functions 124, although AMF 122, NEF 123, andfunctions 124 may differ. Network core 800 comprises Network FunctionVirtualization Infrastructure (NFVI) hardware 801, NFVI hardware drivers802, NFVI operating systems 803, NFVI virtual layer 804, and NFVIVirtual Network Functions (VNFs) 805. NFVI hardware 801 comprisesNetwork Interface Cards (NICs), CPU, RAM, Flash/Disk Drives (DRIVE), andData Switches (SW). NFVI hardware drivers 802 comprise software that isresident in the NIC, CPU, RAM, DRIVE, and SW. NFVI operating systems 803comprise kernels, modules, applications, containers, hypervisors, andthe like. NFVI virtual layer 804 comprises vNIC, vCPU, vRAM, vDRIVE, andvSW. NFVI VNFs 805 comprise Non-3GPP Interworking Function (IWF) 822,Access and Mobility Management Function (AMF) 823, Network ExposureFunction (NEF) 824, Application Function (AF) 825, Session ManagementFunction (SMF) 826, and User Plane Function (UPF) 827. Other VNFs likeAuthentication Server Function (AUSF) and Network Repository Function(NRF) are typically present but are omitted for clarity. Network core800 may be located at a single site or be distributed across multiplegeographic locations. The NIC in NFVI hardware 801 are coupled to ANs420-421 over data links that support NWu, N2, and N1. The NIC in NFVIhardware 801 are coupled to external data systems over data links thatsupport N6. NFVI hardware 801 executes NFVI hardware drivers 802, NFVIoperating systems 803, NFVI virtual layer 804, and NFVI VNFs 805 to formand operate IWF 422, AMF 423, NEF 424, AF 825, SMF 826, and UPF 827.

FIG. 9 further illustrates wireless network core 800 in 5G wirelesscommunication network 400. IWF 422 performs Y2 termination, N2termination, NWu termination, and N1 transfer. AMF 423 performs N1termination, N2 termination, UE ciphering integrity protection, UEregistration and connection, UE mobility and reachability, UEauthentication and authorization, and serves the UE registration API toNEF 423. NEF 424 performs capability and event exposure, datatranslation; abstraction, control-plane management, AF interaction overthe northbound API, and API translations for UE registrations initiatedby AS 402. AF 425 interacts with AS 402 and NEF 424 over the northboundAPI, SMF 426 performs N1 termination, session establishment/management,UPF selection and control, policy and charging control, and trafficsteering and routing. UPF 427 performs packet routing & forwarding,packet inspection and policy, QoS handling and lawful intercept, PDUinterconnection, and mobility anchoring.

In operation, AS 402 transfers a user instruction for UE 401 to AF 425.The user instruction indicates a registration technique, registrationtiming, and networking data. AF 425 translates the user instruction fromAS 402 into a northbound API call. AF 425 transfers northbound API callto NEF 424. NEF 424 translates the NEF API call that has the UEinstruction into an AMF API call that has the UE instruction. In somecase, NEF 424 awaits a time or other condition like UE registration togenerate the AMF API call. NEF 424 transfers the AMF API call that hasthe UE instruction to AMF 423. AMF 423 translates the UE instructioninto a registration message that has a registration cause. AMF 423transfers the registration message with the registration cause to UE 401over an N1 link. AMF 423 may re-register UE 401 to re-authenticate,reboot, change bands, change PLMNs, change slices, change DNNs, orperform another task during re-registration.

FIG. 10 illustrates an exemplary operation of 5G wireless communicationnetwork 400 to register UE 401. The operation may vary in otherexamples. AS 402 transfers an instruction (INST) for UE 101 to AF 425.The user instruction indicates rules for a new registration by UE 101 touse a different PLMN upon UE attachment. AF 425 translates the userinstruction from AS 402 into a northbound (NB) API call. AF 425transfers northbound API call to NEF 424.

UE 401 wirelessly attaches to 5GNR AN 421. UE 401 registers with AMF 423over 5GNR AN 421. In response to an event subscription for UE 401, AMF423 transfer a registration notice for UE 401 to NEF 424. In response tothe northbound API call and the registration notice, NEF 424 translatesthe NEF API call with the UE instruction into an AMF API call with theUE instruction. NEF 424 transfers the AMF API call that has the UEinstruction to AMF 423. AMF 423 translates the UE instruction into aregistration rejection (REJ) that has a registration cause (CZ). AMF 423transfers the registration rejection with the registration cause to UE401 over 5GNR AN 421.

In response to the registration rejection, UE 401 identifies networkingdata based on the registration cause. In this example, the registrationcause comprises an encoded instruction for UE 401 to immediately attachto WIFI AN 420 and register with AMF 423 over a different PLMN. UE 401attaches to WIFI AN 421 and then to IWF 422. UE 401 registers (REG) withAMF 423 over WIFI AN 421 and IWF 422 and requests the different PLMN(INFO). AMF 423 selects and transfers signaling (SIG) to SMF 426 toserve UE 401 over the different PLMN. SMF 426 selects and transferssignaling to UPF 427 to serve UE 401 over the different PLMN. AMF 423transfers signaling to IWF 422 to serve UE 401 over the different PLMN.AMF 423 transfers signaling to UE 401 over IWF 422 and AN 420 to use thedifferent PLMN. UE 401 and WIFI AN 420 wirelessly exchange user dataresponsive to the signaling. WIFI AN 420 and IWF 422 exchange the userdata responsive to the signaling. IWF 422 and UPF 427 exchange the userdata responsive to the signaling. UPF 427 and an external systemexchange the user data responsive to the signaling.

AS 402 transfers a user instruction for UE 101 to AF 425. The userinstruction indicates rules for another registration by UE 401 to use adifferent wireless network slice at a future time. AF 425 translates theuser instruction from AS 402 into northbound API call and transfers thenorthbound API call to NEF 424. NEF 424 translates the northbound APIcall with the user instruction into an AMF API call with a UEinstruction. NEF 424 transfers the AMF API call that has the UEinstruction to AMF 423. AMF 423 translates the other UE instruction intoa deregistration instruction (DEREG) that has a cause (CZ). AMF 423transfers the deregistration instruction with the cause to UE 401 overIWF 422 and WIFI AN 420.

In response to the deregistration instruction, UE 401 identifiesnetworking data based on the cause. In this example, the cause comprisesan encoded instruction for UE 401 to re-register with AMF 423 at afuture time and request a different wireless network slice.Subsequently, UE 401 attaches to WIFI AN 421 and IWF 422. UE 401registers with AMF 423 over WIFI AN 421 and IWF 422 at the future timeand requests the different wireless network slice. AMF 423 transferssignaling to SMF 426 to serve UE 401 over the different wireless networkslice. SMF 426 transfers signaling to UPF 427 to serve UE 401 over thedifferent wireless network slice. AMF 423 transfers signaling to IWF 422to serve UE 401 over the wireless network slice. AMF 423 transferssignaling to UE 401 over IWF 422 and AN 420 to use the wireless networkslice. UE 401 and WIFI AN 420 wirelessly exchange user data responsiveto the signaling. WIFI AN 420 and IWF 422 exchange the user dataresponsive to the signaling. IWF 422 and UPF 427 exchange the user dataresponsive to the signaling. UPF 427 and an external system exchange theuser data responsive to the signaling.

The wireless data network circuitry described above comprises computerhardware and software that form special-purpose network circuitry toregister UEs using new networking data responsive to external control.The computer hardware comprises processing circuitry like CPUs, DSPs,GPUs, transceivers, bus circuitry, and memory. To form these computerhardware structures, semiconductors like silicon or germanium arepositively and negatively doped to form transistors. The dopingcomprises ions like boron or phosphorus that are embedded within thesemiconductor material. The transistors and other electronic structureslike capacitors and resistors are arranged and metallically connectedwithin the semiconductor to form devices like logic circuitry andstorage registers. The logic circuitry and storage registers arearranged to form larger structures like control units, logic units, andRandom-Access Memory (RAM). In turn, the control units, logic units, andRAM are metallically connected to form CPUs, DSPs, GPUs, transceivers,bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAMand the logic units, and the logic units operate on the data. Thecontrol units also drive interactions with external memory like flashdrives, disk drives, and the like. The computer hardware executesmachine-level software to control and move data by driving machine-levelinputs like voltages and currents to the control units, logic units, andRAM. The machine-level software is typically compiled from higher-levelsoftware programs. The higher-level software programs comprise operatingsystems, utilities, user applications, and the like. Both thehigher-level software programs and their compiled machine-level softwareare stored in memory and retrieved for compilation and execution. Onpower-up, the computer hardware automatically executesphysically-embedded machine-level software that drives the compilationand execution of the other computer software components which thenassert control. Due to this automated execution, the presence of thehigher-level software in memory physically changes the structure of thecomputer hardware machines into special-purpose network circuitry toregister UEs using new networking data responsive to external control.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. Thus, the inventionis not limited to the specific embodiments described above, but only bythe following claims and their equivalents.

What is claimed is:
 1. A method of operating a wireless communication network that comprises a Network Exposure Function (NEF) and an Access and Mobility Management Function (AMF) to register a User Equipment (UE), the method comprising: an Application Function (AF) receiving a UE instruction from an external application server, generating a northbound Application Programming Interface (API) call that has the UE instruction, and transferring the northbound API call that has the UE instruction to the NEF; the NEF receiving the northbound API call that has the UE instruction, translating the northbound API call that has the UE instruction into an AMF API call that has the UE instruction, and transferring the AMF API call that has the UE instruction; the AMF receiving the AMF API call that has the UE instruction, translating the UE instruction into a registration message that has a registration cause, and transferring the registration message that has the registration cause; the UE receiving the registration message that has the registration cause, and in response, identifying networking data based on the registration cause and performing a registration based on the networking data; and the AMF transferring the registration message that has the registration cause comprises transferring a registration rejection that has the registration cause responsive to receiving a registration request.
 2. The method of claim 1 wherein the UE identifying the networking data based on the registration cause and performing the registration based on the networking data comprises identifying a UE identifier based on the registration cause and performing an AMF registration based on the UE identifier to re-authenticate the UE.
 3. The method of claim 1 wherein: the AMF comprises a current AMF; and the UE identifying the networking data based on the registration cause and performing the registration based on the networking data comprises identifying a new AMF based on the registration cause and performing a new AMF registration with the new AMF.
 4. The method of claim 1 wherein: the UE is using a current wireless network slice; and the UE identifying the networking data based on the registration cause and performing the registration based on the networking data comprises identifying a new wireless network slice based on the registration cause and performing a new AMF registration based on the new wireless network slice.
 5. The method of claim 1 wherein: the UE is using a current Dynamic Network Name (DNN); and the UE identifying the networking data based on the registration cause and performing the registration based on the networking data comprises identifying a new DNN based on the registration cause and performing a new AMF registration based on the new DNN.
 6. The method of claim 1 wherein: the UE is using a current frequency band; and the UE identifying the networking data based on the registration cause and performing the registration based on the networking data comprises identifying a new frequency band based on the registration cause and performing a new Radio Access Network (RAN) registration based on the new frequency band.
 7. The method of claim 1 wherein: the UE is using a current Public Land Mobile Network (PLMN); and the UE identifying the networking data based on the registration cause and performing the registration based on the networking data comprises identifying a new PLMN based on the registration cause and performing a new Radio Access Network (RAN) registration based on the new PLMN.
 8. The method of claim 1 wherein the UE identifying the networking data based on the registration cause and performing the registration based on the networking data comprises identifying a reboot instruction and rebooting at least a portion of the UE before performing the registration.
 9. The method of claim 1 further comprising: the UE transferring the registration request for the UE; the AMF receiving the registration request for the UE, and in response, transferring a registration notice for the UE; the NEF receiving the registration notice for the UE; and wherein: the NEF transferring the AMF API call that has the UE instruction comprises transferring the AMF API call that has the UE instruction in response to receiving the registration notice for the UE.
 10. The method of claim 1 wherein: the UE instruction comprises an implementation time command that indicates when the user instruction should be implemented; the AMF translating the UE instruction into the registration message and transferring the registration message comprises the AMF translating the UE instruction into the registration message that has the registration cause and the implementation time command and transferring the registration message that has the registration cause and the implementation time command; and the UE receiving the registration message, identifying the networking data, and performing the registration comprises the UE receiving the registration message that has the registration cause and the implementation time command, and in response, identifying networking data based on the registration cause and performing a registration based on the networking data and the implementation time command.
 11. A wireless communication network that comprises a Network Exposure Function (NEF) and an Access and Mobility Management Function (AMF) to register a User Equipment (UE), the wireless communication network comprising: an Application Function (AF) configured to receive a UE instruction from an external application server, generate a northbound Application Programming Interface (API) call that has the UE instruction, and transfer the northbound API call that has the UE instruction to the NEF; the NEF configured to receive the northbound API call that has the UE instruction, translate the northbound API call that has the UE instruction into an AMF API call that has the UE instruction, and transfer the AMF API call that has the UE instruction; the AMF configured to receive the AMF API call that has the UE instruction, translate the UE instruction into a registration message that has a registration cause, and transfer the registration message that has the registration cause; the UE configured to receive the registration message that has the registration cause, and in response, identify networking data based on the registration cause and perform a registration based on the networking data; and the AMF configured to transfer the registration message that has the registration cause comprises transfer a registration rejection that has the registration cause responsive to receiving a registration request.
 12. The wireless communication network of claim 11 wherein the UE is configured to identify a UE identifier based on the registration cause and perform an AMF registration based on the UE identifier to re-authenticate the UE.
 13. The wireless communication network of claim 11 wherein: the AMF comprises a current AMF; and the UE is configured to identify a new AMF based on the registration cause and perform a new AMF registration with the new AMF.
 14. The wireless communication network of claim 11 wherein: the UE is configured to use a current wireless network slice; and the UE is configured to identify a new wireless network slice based on the registration cause and perform a new AMF registration based on the new wireless network slice.
 15. The wireless communication network of claim 11 wherein: the UE is configured to use a current Dynamic Network Name (DNN); and the UE is configured to identify a new DNN based on the registration cause and perform a new AMF registration based on the new DNN.
 16. The wireless communication network of claim 11 wherein: the UE is configured to use a current frequency band; and the UE is configured to identify a new frequency band based on the registration cause and perform a new Radio Access Network (RAN) registration based on the new frequency band.
 17. The wireless communication network of claim 11 wherein: the UE is configured to use a current Public Land Mobile Network (PLMN); and the UE is configured to identify a new PLMN based on the registration cause and perform a new Radio Access Network (RAN) registration based on the new PLMN.
 18. The wireless communication network of claim 11 wherein the UE is configured to identify a reboot instruction and reboot at least a portion of the UE before performing the registration.
 19. The wireless communication network of claim 11 further comprising: the UE configured to transfer the registration request for the UE; the AMF configured to receive the registration request for the UE, and in response, transfer a registration notice for the UE; the NEF is configured to receive the registration notice for the UE; and wherein: the NEF is configured to transfer the AMF API call that has the UE instruction in response to receiving the registration notice for the UE.
 20. The wireless communication network of claim 11 wherein: the UE instruction comprises an implementation time command that indicates when the user instruction should be implemented; the AMF is configured to translate the UE instruction into the registration message that has the registration cause and the implementation time command and transfer the registration message that has the registration cause and the implementation time command; and the UE is configured to receive the registration message that has the registration cause and the implementation time command, and in response, identify networking data based on the registration cause and perform a registration based on the networking data and the implementation time command. 